home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: dd.chalmers.se!news.chalmers.se!sunic!news.funet.fi!ousrvr.oulu.fi!tolsun!kilroy
- From: kilroy@tolsun.oulu.fi (Lauri Aalto)
- Subject: Re: Why does c.o clear BSS? It's not needed!!
- Message-ID: <1994Apr25.132448.26840@ousrvr.oulu.fi>
- Sender: news@ousrvr.oulu.fi
- Organization: University of Oulu, Finland
- References: <80012334@prox.stgt.sub.org> <1994Apr24.121656.9198@ousrvr.oulu.fi> <farrenCosBK0.JC1@netcom.com>
- Date: Mon, 25 Apr 1994 13:24:48 GMT
- Lines: 21
-
- In article <farrenCosBK0.JC1@netcom.com> farren@netcom.com (Mike Farren) writes:
- >kilroy@tolsun.oulu.fi (Lauri Aalto) writes:
- >
- >>Boris Folgmann <boris@prox.stgt.sub.org> writes:
- >>>Why does c.o clear BSS? In the AutoDoc for InternalLoadSeg() you find:
- >
- >>It's an undocumented feature (CLEAR bit on AllocMem()). Some programs rely on
- >>this, so it hasn't been dropped.
- >
- >Pardon me? MEMF_CLEAR is hardly "undocumented" - it's been there for a
- >long, long time.
-
- Sorry for any inconvience I may have caused... I meant that the bss hunk
- clearing with AllocMem()'s CLEAR bit set while allocating memory for the
- hunks is undocumented. That's why most of the C compilers clear the bss
- hunks in a loop before actually using them.
-
- (__) Lauri Aalto
- w \@@/ kilroy@tolsun.oulu.fi
- `/v/-e 2:228/406.2@fidonet
- _/ \_ ...Intel inside--idiot outside...
-